Skip to main content
Version: 2.0

Continuous Improvement

For two decades, I’ve seen engineering teams chase moonshots and incremental gains. Both have their place, but I’ve consistently found the most sustainable success comes from fostering a culture of continuous improvement – not through radical overhauls, but through a relentless pursuit of small, impactful changes. I recently worked with a team struggling to deliver a critical feature. They were stuck in a cycle of ambitious redesigns, each promising a breakthrough but ultimately leading to more delays. By shifting our focus to a series of smaller, iterative improvements – optimizing existing tests, refactoring a troublesome component, and streamlining the deployment process – we not only delivered the feature on time but also significantly boosted team morale. It’s a principle seemingly simple, yet profoundly difficult to implement consistently. This isn’t about a single retrospective or a shiny new process; it’s about weaving a mindset into the fabric of your team.

The Peril of Stifled Improvement​

There's a quiet killer of engineering morale and performance: consistently ignoring good ideas from the team. I’ve seen it happen repeatedly. Someone, often a passionate engineer, identifies a genuine opportunity to improve a process, tool, or even a small piece of code. They voice it. Maybe even voice it multiple times. And if leadership consistently brushes it aside – not because it’s bad but because “it’s not the right time,” or “we have other priorities,” or simply through inaction – something breaks.

That engineer, rightfully feeling unheard and undervalued, will eventually realize their potential is being stifled. They'll disengage, and ultimately, they'll leave. And with them goes not only their skillset but also a valuable piece of the team’s innovative spirit.

This isn’t just about being “nice.” It’s about recognizing that the people doing the work are often the best equipped to identify opportunities for improvement. Ignoring their input is a guaranteed path to stagnation and attrition.

Beyond "Do More Faster": The Right Kind of Speed​

The mantra “Do More Faster,” popularized by TechStars (https://www.techstars.com/), has a seductive appeal. But speed without direction, or without addressing underlying inefficiencies, is a recipe for burnout and technical debt. True continuous improvement isn’t about accelerating existing processes; it’s about optimizing them.

Think of it like this: a faster horse pulling a heavier load doesn't get you to your destination any quicker if the road is riddled with potholes. Your focus needs to be on smoothing the road, not just urging the horse to run faster.

Building a System for Incremental Wins​

So, how do you cultivate a culture of continuous improvement? Here's a framework built from experience:

  • Create Safe Spaces for Feedback: Regular retrospectives are essential, but they aren't enough. Encourage informal feedback channels – dedicated Slack channels, "office hours" with engineering managers, or even anonymous suggestion boxes. The key is to make it easy and safe to voice ideas, no matter how small.
  • Prioritize & Experiment: You can’t act on every suggestion. Implement a lightweight prioritization system – perhaps based on impact/effort. Crucially, frame improvements as experiments. “Let's try X for one sprint and see if it improves Y.” This lowers the risk and allows for quick iteration.
  • Empower Ownership: Don’t just assign improvements; empower team members to own them. Let them lead the effort, from implementation to monitoring results. This fosters a sense of responsibility and pride.
  • Celebrate Small Wins: Publicly acknowledge and celebrate even the smallest improvements. A quick shout-out in a team meeting, a post in a Slack channel, or a simple “thank you” can go a long way in reinforcing positive behavior.
  • Data-Driven Validation: As Christen Lassenius's research on team retrospectives demonstrates, it’s not enough to discuss improvements. You need to validate them. Lassenius’s work emphasizes the importance of actionable retrospectives – those that lead to measurable changes and demonstrable results. Track key metrics before and after implementing a change to objectively measure its impact. This moves the conversation from subjective opinions to empirical evidence.

The Importance of Data and Scaling Improvement​

It's easy to fall into the trap of thinking you know what’s best. But the most effective improvements often come from unexpected places. That's why data-driven validation is so crucial.

Consider this: you might assume a new CI/CD pipeline will significantly reduce deployment time. But without tracking actual deployment metrics before and after implementation, you're operating on an assumption. The data might reveal that the new pipeline only marginally improves deployment time, but introduces new complexities that outweigh the benefits.

Furthermore, while team-level retrospectives are valuable, don't stop there. Consider how to scale these practices organization-wide. How can you share learnings between teams? How can you ensure that improvements at the team level align with broader organizational goals? This requires intentional effort and cross-functional collaboration. One approach is to establish a community of practice where teams can share best practices and lessons learned.

Final Thoughts​

Continuous improvement isn’t a destination; it’s a journey. It requires a shift in mindset, a commitment to experimentation, and a relentless focus on small, impactful changes. By empowering your team to identify and implement these changes, you’ll not only improve your engineering processes but also cultivate a more engaged, motivated, and innovative workforce. And that, in the long run, is the most valuable improvement of all.